Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

support for Oracle Linux #2776

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

support for Oracle Linux #2776

wants to merge 3 commits into from

Conversation

jserviceorg
Copy link

Which issue(s) this PR fixes:
Fixes #

This adds Oracle Linux support for on premise installations. Oracle Linux is basically just another RHEL clone like Rocky.

What type of PR is this?
/kind feature

Special notes for your reviewer:

@kubermatic-bot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubermatic-bot
Copy link
Contributor

@jserviceorg: Adding the "do-not-merge/docs-needed" label because no documentation block was detected, please follow our documentation process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubermatic-bot kubermatic-bot added kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. labels Apr 26, 2023
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign moadqassem for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 26, 2023
@kubermatic-bot
Copy link
Contributor

Hi @jserviceorg. Thanks for your PR.

I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubermatic-bot kubermatic-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. dco-signoff: no Denotes that at least one commit in the pull request doesn't have a valid DCO signoff message. labels Apr 26, 2023
@jgotteswinter @jserviceorg
initial ol support
b709713 
Signed-off-by: Juergen Gotteswinter <mail@jservice.org>
@jgotteswinter @jserviceorg
ol fixes
e2264d5 
Signed-off-by: Juergen Gotteswinter <mail@jservice.org>
@jgotteswinter @jserviceorg
more ol fixes
9a9c5ff 
Signed-off-by: Juergen Gotteswinter <mail@jservice.org>
@kubermatic-bot kubermatic-bot added dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. and removed dco-signoff: no Denotes that at least one commit in the pull request doesn't have a valid DCO signoff message. labels Apr 26, 2023
@kron4eg
Copy link
Member

kron4eg commented May 5, 2023

@jserviceorg thank you for your efforts!

Before we can proceed on this, please take a look at the https://github.com/kubermatic/kubeone/blob/main/docs/adding_provider_support.md, especially Prerequisites section. Please keep in mind, this doc has been written prior we even had an idea about OSM that we are currently using. I mean, besides integrating to machine-controller you will also need an OperatingSystemProfile object integrated in OSM project.

Once MC and OSM has support for new OS, then and only then we can integrate it to Kubeone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/feature Categorizes issue or PR as related to a new feature. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@jserviceorg @kubermatic-bot @kron4eg @jgotteswinter